Smart and scalable touch user interface display

ABSTRACT

Aspects of the present disclosure relate to systems and methods for displaying a touchable user interface of a display device and displaying a user interface progress experience on the touchable user interface. In one aspect, available application space on the display device may be identified. An amount of available application space may be comparted with an amount of space required for one or more user interface elements. A visible display of the one or more user interface elements may be adjusted based on the amount of available application space compared to the amount of space required for the one or more user interface elements. In another aspect, an action command associated with the one or more user interface elements may be selected and performed. While the selected action command is being performed and when a threshold value has been met, the user interface progress experience may be displayed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/018,290, filed Jun. 27, 2014, entitled “SMART ANDSCALABLE TOUCH USER INTERFACE DISPLAY,” which application isincorporated herein by reference in its entirety.

BACKGROUND

Computer and software users have grown accustomed to user-friendlysoftware applications that help them write, calculate, organize, preparepresentations, send and receive electronic mail, make music, and thelike. For example, word processing applications allow users to prepare avariety of useful documents. Spreadsheet applications allow users toenter, manipulate, and organize data. Electronic slide presentationapplications allow users to create a variety of slide presentationscontaining text, pictures, data or other useful objects.

To assist users to locate and utilize software applications, a userinterface containing a plurality of command controls is typicallyprovided along an upper, lower or side edge of a displayed workspace inwhich the user may enter, copy, manipulate and format text or data. Suchcommands often include selectable buttons with such names as “file,”“edit,” “view,” “insert,” “format,” and the like. Typically, selectionof one of these top-level buttons, for example “format,” causes adrop-down menu or a bar to be deployed to expose one or more selectablecontrols associated with the top-level buttons, for example “font” undera top-level functionality of “format.” However, as computing devicesdecrease in size, so too does the amount of screen space available forthe display of the workspace, controls, and commands.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

In summary, the disclosure generally relates to an improved touch userinterface for displaying and scaling software applications and/orselectable controls. More particularly, the disclosure relates togranular scaling of software applications (e.g., user interfaceelements) on a touchable user interface display to accommodate differentwindow sizes, device sizes, and/or a change in window or device size.

DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.

FIG. 1 is illustrates an exemplary computing device equipped with atouchable user interface, according to an example aspect.

FIG. 2 illustrates an exemplary touchable user interface of a softwareapplication for displaying user interface elements, according to anexample aspect.

FIG. 3 illustrates an exemplary touchable user interface of a softwareapplication for displaying a user interface progress experience,according to an example aspect.

FIG. 4 illustrates an exemplary method for dynamically scaling userinterface elements of a software application displayed on a touchableuser interface of a computing device, according to an example aspect.

FIG. 5 illustrates an exemplary method for displaying a user interfaceprogress experience on a touchable user interface of a computing device,according to an example aspect.

FIG. 6 is a block diagram illustrating example physical components of acomputing device with which aspects of the disclosure may be practiced.

FIGS. 7A and 7B are simplified block diagrams of a mobile computingdevice with which aspects of the present disclosure may be practiced.

FIG. 8 is a simplified block diagram of a distributed computing systemin which aspects of the present disclosure may be practiced.

FIG. 9 illustrates a tablet computing device for executing one or moreaspects of the present disclosure.

DETAILED DESCRIPTION

Aspects of the disclosure are directed to an improved graphical userinterface. As discussed above, smaller and smaller computing devices arebeing designed and utilized. As computing devices decrease in size, sotoo does the size of their display screens. Accordingly, the windowsdisplaying the software applications are also small in size. The smallwindows provide less space to display the workspace (also referred to asa “canvas”) and selectable commands and controls.

To address the above limitations, aspects of the disclosure relategenerally to methods and systems for an improved touchable userinterface. The improved touchable user interface displays and granularlyscales selectable software applications and images within a workspacebased on the size of the window displaying the software applicationand/or image or a change in the size or orientation of the window. Inturn, the improved touchable user interface facilitates an efficient,simple, and easy one touch interface for manipulating softwareapplications.

Referring now to the drawings, in which like numerals represent likeelements through the several figures, aspects of the present inventionand the exemplary operating environment will be described. FIG. 1 andthe following discussion are intended to provide a brief, generaldescription of a suitable computing environment in which the inventionmay be implemented. Referring now to FIG. 1 an example computing device100 equipped with a touch screen, such as a tablet computer or a mobilephone, for example, is shown. As used herein, a touch screen includes atouchable user interface 102 that is capable of receiving input viacontact with the screen, thereby functioning as both an input device andan output device. For example, content may be displayed, or output, onthe screen and input may be received by contacting the screen using astylus or by direct physical contact of a user, e.g., touching thescreen. Contact may include, for instance, tapping the screen, usinggestures such as swiping or pinching the screen, sketching on thescreen, etc. As illustrated, the touchable user interface 102 displayedon the computing device 100 includes a canvas 104 and a contextual panel106. The canvas 104 may display user interface elements 108. Thecontextual panel 106 may include software application information 112and/or a plurality of individual selectable controls 214 (as shown inFIG. 2).

As described herein, the user interface elements 108 representselectable elements. Generally, the user interface elements 108 referto, for example, thumbnails, which represent a scaled down version ofsoftware applications and/or images such as documents, spreadsheets,presentation slides, and other objects. Accordingly, the user interfaceelements 108 contain readily utilized functionality when opening,creating, saving and/or viewing a software application using thetouchable user interface 102. In this regard, aspects of the presentdisclosure make it possible for a user to have easy access to such userinterface elements positioned on touchable user interface 102 such thatsoftware applications may be launched with a single touch and/or handgesture from a start screen of the touchable user interface 102.

A user may work with and/or manipulate a new document and/or an existingdocument using the touchable user interface 102. In the exemplary aspectof FIG. 1, the user interface elements 108 include a plurality ofvarious types of documents and/or templates. For example, the differenttypes of documents and/or templates may include a blank document, acorporate report template, a calendar, a resume, a checklist, a journaldocument, and a home buying document, to name a few. In this regard, auser may open and create a new document of the user's choice from astart screen with a simple, single touch and/or hand gesture using thetouchable user interface 102. As discussed above, the contextual panel106 may include software application information 112 and/or a pluralityof individual selectable controls 214 (as shown in FIG. 2). In thisregard, the contextual panel 106 is a designated area or space displayedon the touchable user interface 102 that organizes and provides commandsand/or controls for selection by the user of the application. In someaspects, the contextual panel 106 is located to the left of the canvas104. In other aspects, the contextual panel 106 is located to right,above or below the canvas 104. The software application information 112may include a list of existing documents. In the exemplary aspectdepicted in FIG. 1, the software application information 112 includes alist of recently created Word documents including the date of when theexisting documents were created and/or edited. The contextual panel 106may additionally include a selectable option 116 for opening documentsother than the documents included in the software applicationinformation 112.

In some aspects, when a user selects a new document or an existingdocument from the touchable user interface 102, the selected documentmay be displayed at full size such that the selected document occupiesthe entire display (e.g., all of the touchable user interface 102). Asdiscussed above, detection of a user selection may include, for example,detection of a single touch or hand gesture which may include tapping,clicking, or highlighting an area of the touchable user interface 102,such as, tapping, clicking, or highlighting a user interface element108, software application information 112 and/or a selectable control214.

FIG. 2 illustrates a touchable user interface 202 for creating a newdocument according to one or more aspects. Similar to the touchable userinterface 102 described above relative to FIG. 1, the touchable userinterface 202 includes a canvas 204 and a contextual panel 206. Thecanvas 204 may include user interface elements 208 (e.g., such as theuser interface elements 108 described above relative to FIG. 1). Thecontextual panel 206 may include selectable controls 214. For instance,such selectable controls may be general file commands such as “new,”“open,” “save,” “save as,” “print,” “share,” “close,” and “settings.”Aspects are not limited to these example selectable controls, and itshould be appreciated that any number of selectable controls may beincluded in an initial or adjusted display of contextual panel 206.According to one aspect, the selectable controls 214 included in thecontextual panel 206 may be controls that are generally found and usedacross a number of different software applications.

As shown in FIG. 2, the user interface elements 208 may be arranged anddisplayed in the canvas 204 as a grid layout with two rows and fourcolumns. However, depending on the size of the canvas 204 (e.g., thesize of the touch screen window space), the layout of the user interfaceelements 208 may change. For example, the number of rows and columns maybe scaled based on the screen resolution and based on how many userinterface elements 208 can be displayed in the canvas 204. In thisregard, as the screen size gets smaller (e.g., when a user utilizes amobile device instead of a tablet device) less user interface elements208 may be displayed on the screen. In one example, the number ofcolumns of user interface elements 208 is reduced when the screen sizeis reduced. In one aspect, the size of the user interface elements 208does not change as the screen size changes. In another aspect, the sizeof the user interface elements 208 may change as the screen size changessuch that the same number of user interface elements 208 is displayedregardless of the size of the screen. In yet another aspect, the size ofthe user interface elements 208 may change and the number of columns ofuser interface elements 208 may change when the screen size changes.

As such, the software application executed by the computing device 100calculates a layout for the touchable user interface 102/202. In orderto calculate an appropriate layout for the touchable user interface102/202, the application has to identify the current window size of thesoftware application utilized by a user. Identifying the window size ofthe software application includes identifying a change in the windowsize of the application. A window may change in size due to userselection (such as resizing of the window), based on a change of displayscreen for the computing device (such as changing from one monitor to amonitor of a different size), a change in device orientation betweenportrait and landscape, or based on a change in computing device. Insmaller computer devices (such as phones, tablets, watches, and etc.),the window size of the application may correspond to the size and/ororientation of the display screen of the touchable user interface102/202.

In one aspect, a layout (e.g., the layout shown in FIG. 2) is calculatedby utilizing a priority list. In some aspects, the priority listidentifies what user interface elements 208 are displayed in the canvas204 and/or potential selectable controls 214 are displayed in thecontextual panel 206 for various potential application window sizes. Thepriority list calculates scaling for any potential window size. In someaspects, the priority list calculates scaling for any potential windowsize up to a predetermined maximum window size and/or down to apredetermined minimum window size. In further aspects, the window sizeis calculated and/or identified by the priority list along with scaling.In some aspects, the priority list may cache or save some layouts thathave already been computed for a certain device, (e.g. full screenlandscape, full screen portrait), but the scaling logic utilized by thepriority list does not have to rely on these saved layouts.

A user interface element 208 and/or other items may be displayed ordesignated utilizing a graphical representation. In some aspects, thepriority list further identifies whether the user interface element 208and/or other items should change in size based on an identified windowsize. In additional aspects, the priority list further identifieswhether the spacing between a user interface element 208 and anotheritem should change in size based on an identified window size. In someaspects, the canvas 204 of the touchable user interface 202 may bescaled such that an even number of user interface elements 208 aredisplayed. In one aspect, 24 user interface elements 208 may bedisplayed. In this example, the 24 user interface elements 208 may bescaled and displayed in various orientations as the screen size changes.The various orientations may include at least 24 rows by 1 column, 12rows by 2 columns, 8 rows by 3 columns, 6 rows by 4 columns, 4 rows by 6columns, 3 rows by 8 columns, 2 rows by 12 columns, and 1 row by 24columns.

FIG. 3 illustrates a user interface 302 including a user interfaceprogress experience 310 according to one or more aspects. The userinterface progress experience 310 may indicate the status of an actionassociated with a user interface element 208. For example, if the userinterface element 208 is a new Word document that a user wants tocreate, after the user selects (e.g., by touching the Word documentusing the user interface 302) the new Word document, the user interfaceprogress experience 310 may show an opening status of the new Worddocument. In one aspect, the user interface progress experience 310 isdisplayed after a threshold value has been met. In this regard, in theexample discussed above, if the new Word document opens before thethreshold value has been met, the user interface progress experience 310will not be displayed. However, if the new Word document does not openbefore the threshold value has been met; the user interface progressexperience 310 will be displayed after the threshold value has been met.For example, if the threshold value is 2 seconds, the user interfaceprogress experience 310 will be displayed after 2 seconds if the newword document is still in the process of opening after 2 seconds. Whenthe process of opening the new Word document concludes, the userinterface progress experience 310 is hidden from the display.

In one aspect, the user interface 302 may include a cancel button forcanceling the action associated with a user interface element 208 and/orthe display of the user interface progress experience 310. In thisregard, while the user interface progress experience 310 displays thestatus of a document and while the action associated with the documentis being performed, a user may select a cancel button. When the cancelbutton is selected, the user interface progress experience 310 may behidden from the display and the software application may return to itsprevious state.

The action associated with a user interface element 208 may include anyaction capable of being performed in relation to a user interfaceelement 208 such as opening, saving, creating, and sharing, to name afew. The threshold value associated with displaying the user interfaceprogress experience 310 may be any threshold value suitable for theassociated software application. For example, the threshold value may bebased on avoiding a flickering of the user interface progress experience310 in situations when an action is performed and completed in a shortperiod of time.

Although FIG. 3 is described with respect to the user interface 302, itcan be appreciated that the functionality described with respect to theuser interface 302 may be implemented on a non-touch device. In oneexample, a tablet device may be utilized as a non-touch device when itis docked at a docking station. In this example, the functionalitydescribed above relative to the user interface 302 may be implementedusing a cursor, for example. In this regard, in the example describedabove, after the user selects (e.g., by placing a cursor on the Worddocument using a device such as a mouse) the new Word document, the userinterface progress experience 310 may show an opening status of the newWord document.

Referring now to FIG. 4, an exemplary method 400 for dynamically scalinguser interface elements of a software application displayed on atouchable user interface of a computing device, according to an exampleaspect is shown. Method 400 may be implemented on a computing device ora similar electronic device capable of executing instructions through atleast one processor. The improved touchable user interface may bedisplayed by any suitable software application. For example, thesoftware application may be one of an email application, a socialnetworking application, project management application, a collaborationapplication, an enterprise management application, a messagingapplication, a word processing application, a spreadsheet application, adatabase application, a presentation application, a contactsapplication, a calendaring application, and etc. This list is exemplaryonly and should not be considered as limiting. Any suitable applicationfor displaying the improved touchable user interface may be utilized bymethod 400.

The computing device may be any suitable computing device for executingan application. Any suitable computing device may be utilized by method400 for executing the application and displaying the improved touchableuser interface. For example, the computing device may be at least oneof: a mobile telephone; a smart phone; a tablet; a smart watch; awearable computer; a personal computer; a desktop computer; a laptopcomputer; and etc. This list is exemplary only and should not beconsidered as limiting. Any suitable computing device or display devicefor executing the software application displaying the improved touchableuser interface may be utilized by method 400.

Method 400 may begin at operation 402, where an amount of availableapplication space is identified. In order to calculate the appropriatelayout for the touchable user interface, an available application widthor height may be identified or calculated. According to aspects of thedisclosure, such calculations of available application space may involveascertaining a number of available pixels in a given visual environment.In some instances, the available application width or height maycorrespond to an amount of window space available (e.g., within theparameters of a document open on a smartphone or other device when noother applications are open). In other instances, the availableapplication width or height corresponds only to an amount of spaceavailable within the application upon execution (e.g., within theparameters of a document open on a tablet or other device when otherapplications are also open). Identifying the window size of theapplication may include identifying any changes in the window size ofthe application. A display screen may change in size due to userselection or based on a change in display screen for the computingdevice. In smaller computer devices (such as phones, tablets, watches,and etc.), the window size of the application may correspond to the sizeof the display screen. In some instances, identifying an amount ofavailable space may include identifying a change in an amount ofavailable space, such as, when a user rotates a device to change itsorientation or manually reduces an application size within a window.

Flow may proceed to operation 404, where a comparison is made betweenthe amount of space available and the amount of space needed for theuser interface elements. Upon identifying the available space, acomponent of the application executed by the computing device maycalculate a layout for the touchable user interface. To perform suchcalculations, one or more application components may first calculate thesize of each element. For instance, a pixel size may be determined foreach element and/or region. A total available size needed to accommodatethe touchable user interface may then be summed from the individualcalculations. Depending upon the amount of space available to theapplication (e.g., due to screen size constraints, application windowsize adjustments, device type, etc.), each region of the touchable userinterface may be constrained in terms of how many, if any, of the userinterface elements, if any, may be displayed. Accordingly, to adjust toavailable space within a screen, the touchable user interface may firstdetermine, for example, how many pixels each region encompasses, and maysum the pixel amounts to identify a total pixel size. A comparison maythen be made between the total size needed and the amount of spaceavailable.

Upon identifying an amount of available space, flow may proceed tooperation 406, where the visual display of the user interface elementsmay be adjusted. Accordingly, when insufficient space is available inthe touchable user interface for displaying regions, a determination maybe made at application run time as to any regions that may be scaled oreliminated. For instance, an amount of available space may be calculatedbased on screen width in pixels (e.g., 768 pixels), or a change in widthor height from one pixel amount to 768 pixels, 500 pixels, or any otherreduction/enlargement in pixel size may be detected. For instance, ifthe user manually reduces the size of the touchable user interface, orrotates the device so that the screen orientation changes, a similardetermination may be made as to the available space for displaying theregions. As should be appreciated, a determination may be made as to theorder of truncating functional or informational regions, as well as fordetermining which selectable functionality control sections aredisplayed and which sections are collapsed as the available space in theuser interface is decreased.

Referring now to FIG. 5, an exemplary method 500 for displaying a userinterface progress experience on a touchable user interface of acomputing device, according to an example aspect is shown. Method 500begins at operation 502 where a selection of an action command isreceived. The action command may be received by a processor when a userselects (e.g., touches) a user interface element and/or a selectablecontrol on the touchable user interface. The action command may includeany action capable of being performed in relation to a user interfaceelement such as opening, saving, creating, and sharing, to name a few.

After the action command is received, flow proceeds to operation 504where the selected action is performed. For example, if the selectedaction is opening a document, the process of opening the selecteddocument is performed. In another example, if the selected action issaving a document, the process of saving the selected document isperformed. While the selected action is being performed, flow proceedsto operation 506 where it is determined whether the selected action hasbeen completed. In the example regarding opening a document, determiningwhether the selected action has been completed includes determiningwhether the document has opened. If the action has been completed (e.g.,if the document has been opened), flow proceeds back to operation 502where a selection of a new action command may be received. If the actionhas not been completed, flow proceeds to operation 508 where it isdetermined whether a threshold value has been met. The threshold valueis associated with displaying the user interface progress experience.The threshold value may be any threshold value suitable for theassociated software application. For example, the threshold value may bebased on avoiding a flickering of the user interface progress experiencein situations when an action is performed and completed in a shortperiod of time. In one aspect, the threshold value is two seconds.

If the threshold value has not been met, flow proceeds back to operation506 where it is determined whether the action has been completed. If thethreshold value has been met, flow proceeds to operation 510 where theuser interface progress experience is displayed. The user interfaceprogress experience may indicate the status of the selected action as itis performed. For example, after the threshold value has been met, theuser interface progress experience may be displayed such that the userinterface progress experience shows the status of the selected action asit is being performed. In the example of opening a document, the userinterface progress experience may show that the document is being openedby displaying text such as, “opening document.” When the actionperformed is complete, the user interface progress experience may behidden from the display.

Techniques for providing a scalable touchable user interface aredescribed. Although aspects are described in language specific tostructural features and/or methodological acts, it is to be understoodthat the aspects defined in the appended claims are not necessarilylimited to the specific features or acts described above. Rather, thespecific features and acts are disclosed as example forms ofimplementing the claimed aspects.

A number of methods may be implemented to perform the techniquesdiscussed herein. Aspects of the methods may be implemented in hardware,firmware, or software, or a combination thereof. The methods are shownas a set of blocks that specify operations performed by one or moredevices and are not necessarily limited to the orders shown forperforming the operations by the respective blocks. Further, anoperation shown with respect to a particular method may be combinedand/or interchanged with an operation of a different method inaccordance with one or more implementations. Aspects of the methods maybe implemented via interaction between various entities discussed abovewith reference to the touchable user interface.

The aspects and functionalities described herein may operate via amultitude of computing systems including, without limitation, desktopcomputer systems, wired and wireless computing systems, mobile computingsystems (e.g., mobile telephones, netbooks, tablet or slate typecomputers, notebook computers, and laptop computers), hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, and mainframe computers.

In addition, the aspects and functionalities described herein mayoperate over distributed systems (e.g., cloud-based computing systems),where application functionality, memory, data storage and retrieval andvarious processing functions may be operated remotely from each otherover a distributed computing network, such as the Internet or anintranet. User interfaces and information of various types may bedisplayed via on-board computing device displays or via remote displayunits associated with one or more computing devices. For example, userinterfaces and information of various types may be displayed andinteracted with on a wall surface onto which user interfaces andinformation of various types are projected. Interaction with themultitude of computing systems with which aspects of the invention maybe practiced include, keystroke entry, touch screen entry, voice orother audio entry, gesture entry where an associated computing device isequipped with detection (e.g., camera) functionality for capturing andinterpreting user gestures for controlling the functionality of thecomputing device, and the like.

FIGS. 6-8 and the associated descriptions provide a discussion of avariety of operating environments in which aspects of the disclosure maybe practiced. However, the devices and systems illustrated and discussedwith respect to FIGS. 6-8 are for purposes of example and illustrationand are not limiting of a vast number of computing device configurationsthat may be utilized for practicing aspects of the disclosure, describedherein

FIG. 6 is a block diagram illustrating physical components (e.g.,hardware) of a computing device 600 with which aspects of the disclosuremay be practiced. The computing device components described below may becomputer executable instructions for an email application 660, wordprocessing application 662, database application 664, slide presentationapplication 668, spreadsheet application 670, and any other suitableapplication that can be executed to employ the methods 400 and 500disclosed herein. In a basic configuration, the computing device 600 mayinclude at least one processing unit 602 and a system memory 604.Depending on the configuration and type of computing device, the systemmemory 604 may comprise, but is not limited to, volatile storage (e.g.,random access memory), non-volatile storage (e.g., read-only memory),flash memory, or any combination of such memories. The system memory 604may include an operating system 605 and one or more program modules 606suitable for running software applications 620 utilizing the improvedtouchable user interface as illustrated in FIGS. 1-3. The operatingsystem 605, for example, may be suitable for controlling the operationof the computing device 600. Furthermore, aspects of the disclosure maybe practiced in conjunction with a graphics library, other operatingsystems, or any other application program and is not limited to anyparticular application or system. This basic configuration isillustrated in FIG. 6 by those components within a dashed line 608. Thecomputing device 600 may have additional features or functionality. Forexample, the computing device 600 may also include additional datastorage devices (removable and/or non-removable) such as, for example,magnetic disks, optical disks, or tape. Such additional storage isillustrated in FIG. 6 by a removable storage device 609 and anon-removable storage device 610.

As stated above, a number of program modules and data files may bestored in the system memory 604. While executing on the processing unit602, the program modules 606 may perform processes including, but notlimited to, the aspects, as described herein. Other program modules thatmay be used in accordance with aspects of the present disclosure, and inparticular to generate screen content, may include electronic mail andcontacts applications, contact applications, drawing applications,messaging applications, calendaring applications, a social networkingapplication, project management application, a collaborationapplication, an enterprise management application, and/or etc.

Furthermore, aspects of the disclosure may be practiced in an electricalcircuit comprising discrete electronic elements, packaged or integratedelectronic chips containing logic gates, a circuit utilizing amicroprocessor, or on a single chip containing electronic elements ormicroprocessors. For example, aspects of the disclosure may be practicedvia a system-on-a-chip (SOC) where each or many of the componentsillustrated in FIG. 6 may be integrated onto a single integratedcircuit. Such an SOC device may include one or more processing units,graphics units, communications units, system virtualization units andvarious application functionality all of which are integrated (or“burned”) onto the chip substrate as a single integrated circuit. Whenoperating via an SOC, the functionality, described herein, with respectto the capability of client to switch protocols may be operated viaapplication-specific logic integrated with other components of thecomputing device 600 on the single integrated circuit (chip). Aspects ofthe disclosure may also be practiced using other technologies capable ofperforming logical operations such as, for example, AND, OR, and NOT,including but not limited to mechanical, optical, fluidic, and quantumtechnologies. In addition, aspects of the disclosure may be practicedwithin a general purpose computer or in any other circuits or systems.

The computing device 600 may also have one or more input device(s) 612such as a keyboard, a mouse, a pen, a sound or voice input device, atouch or swipe input device, etc. The output device(s) 614 such as adisplay, speakers, a printer, etc. may also be included. Theaforementioned devices are examples and others may be used. Thecomputing device 600 may include one or more communication connections616 allowing communications with other computing devices 650. Examplesof suitable communication connections 616 include, but are not limitedto, RF transmitter, receiver, and/or transceiver circuitry; universalserial bus (USB), parallel, and/or serial ports.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, or program modules. The system memory604, the removable storage device 609, and the non-removable storagedevice 610 are all computer storage media examples (e.g., memorystorage) Computer storage media may include RAM, ROM, electricallyerasable read-only memory (EEPROM), flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other article of manufacturewhich can be used to store information and which can be accessed by thecomputing device 600. Any such computer storage media may be part of thecomputing device 600. Computer storage media does not include a carrierwave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, andincludes any information delivery media. The term “modulated datasignal” may describe a signal that has one or more characteristics setor changed in such a manner as to encode information in the signal. Byway of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), infrared, andother wireless media.

FIGS. 7A and 7B illustrate a mobile computing device 700, for example, amobile telephone, a smart phone, wearable computer (such as a smartwatch), a tablet personal computer, a laptop computer, a desktopcomputer, and the like, with which aspects of the disclosure may bepracticed. In some aspects, the client may be a mobile computing device.With reference to FIG. 7A, one aspect of a mobile computing device 700for implementing the aspects is illustrated. In a basic configuration,the mobile computing device 700 is a handheld computer having both inputelements and output elements. The mobile computing device 700 typicallyincludes a display 705 and one or more input buttons 710 that allow theuser to enter information into the mobile computing device 700. Thedisplay 705 of the mobile computing device 700 may also function as aninput device (e.g., a touch screen display). If included, an optionalside input element 715 allows further user input. The side input element715 may be a rotary switch, a button, or any other type of manual inputelement. In alternative aspects, mobile computing device 700 mayincorporate more or less input elements. For example, the display 705may not be a touchpad in some aspects. In yet another alternativeaspect, the mobile computing device 700 is a portable phone system, suchas a cellular phone. The mobile computing device 700 may also include anoptional keypad 735. Optional keypad 735 may be a physical keypad or a“soft” keypad generated on the touch screen display. In various aspects,the output elements include the display 705 for showing a graphical userinterface (GUI), a visual indicator 720 (e.g., a light emitting diode),and/or an audio transducer 725 (e.g., a speaker). In some aspects, themobile computing device 700 incorporates a vibration transducer forproviding the user with tactile feedback. In yet another aspect, themobile computing device 700 incorporates input and/or output ports, suchas an audio input (e.g., a microphone jack), an audio output (e.g., aheadphone jack), and a video output (e.g., a HDMI port) for sendingsignals to or receiving signals from an external device.

FIG. 7B is a block diagram illustrating the architecture of one aspectof a mobile computing device. That is, the mobile computing device 700can incorporate a system (e.g., an architecture) 702 to implement someaspects. In one aspect, the system 702 is implemented as a “smart phone”capable of running one or more applications (e.g., browser, e-mail,calendaring, contact managers, messaging clients, games, and mediaclients/players). In some aspects, the system 702 is integrated as acomputing device, such as an integrated personal digital assistant (PDA)and wireless phone.

One or more application programs 766 may be loaded into the memory 762and run on or in association with the operating system 764. Examples ofthe application programs include phone dialer programs, e-mail programs,personal information management (PIM) programs, word processingprograms, spreadsheet programs, Internet browser programs, messagingprograms, and so forth. The system 702 also includes a non-volatilestorage area 768 within the memory 762. The non-volatile storage area768 may be used to store persistent information that should not be lostif the system 702 is powered down. The application programs 766 may useand store information in the non-volatile storage area 768, such ase-mail or other messages used by an e-mail application, and the like. Asynchronization application (not shown) also resides on the system 702and is programmed to interact with a corresponding synchronizationapplication resident on a host computer to keep the information storedin the non-volatile storage area 768 synchronized with correspondinginformation stored at the host computer. As should be appreciated, otherapplications may be loaded into the memory 762 and run on the mobilecomputing device 700, including the instructions to scale a softwareapplication including a touchable user interface as described herein.

The system 702 has a power supply 770, which may be implemented as oneor more batteries. The power supply 770 might further include anexternal power source, such as an AC adapter or a powered docking cradlethat supplements or recharges the batteries.

The system 702 may also include a radio 772 that performs the functionof transmitting and receiving radio frequency communications. The radio772 facilitates wireless connectivity between the system 702 and the“outside world,” via a communications carrier or service provider.Transmissions to and from the radio 772 are conducted under control ofthe operating system 764. In other words, communications received by theradio 772 may be disseminated to the application programs 766 via theoperating system 764, and vice versa.

The visual indicator 720 may be used to provide visual notifications,and/or an audio interface 774 may be used for producing audiblenotifications via the audio transducer 725. In the illustrated aspect,the visual indicator 720 is a light emitting diode (LED) and the audiotransducer 725 is a speaker. These devices may be directly coupled tothe power supply 770 so that when activated, they remain on for aduration dictated by the notification mechanism even though theprocessor 760 and other components might shut down for conservingbattery power. The LED may be programmed to remain on indefinitely untilthe user takes action to indicate the powered-on status of the device.The audio interface 774 is used to provide audible signals to andreceive audible signals from the user. For example, in addition to beingcoupled to the audio transducer 725, the audio interface 774 may also becoupled to a microphone to receive audible input, such as to facilitatea telephone conversation. In accordance with aspects of the presentdisclosure, the microphone may also serve as an audio sensor tofacilitate control of notifications, as will be described below. Thesystem 702 may further include a video interface 776 that enables anoperation of an on-board camera 730 to record still images, videostream, and the like.

A mobile computing device 700 implementing the system 702 may haveadditional features or functionality. For example, the mobile computingdevice 700 may also include additional data storage devices (removableand/or non-removable) such as, magnetic disks, optical disks, or tape.Such additional storage is illustrated in FIG. 7B by the non-volatilestorage area 768.

Data/information generated or captured by the mobile computing device700 and stored via the system 702 may be stored locally on the mobilecomputing device 700, as described above, or the data may be stored onany number of storage media that may be accessed by the device via theradio 772 or via a wired connection between the mobile computing device700 and a separate computing device associated with the mobile computingdevice 700, for example, a server computer in a distributed computingnetwork, such as the Internet. As should be appreciated suchdata/information may be accessed via the mobile computing device 700 viathe radio 772 or via a distributed computing network. Similarly, suchdata/information may be readily transferred between computing devicesfor storage and use according to well-known data/information transferand storage means, including electronic mail and collaborativedata/information sharing systems.

FIG. 8 illustrates one aspect of the architecture of a system forprocessing data received at a computing system from a remote source,such as a computing device 804, tablet 806, or mobile device 808, asdescribed above. Content displayed at server device 802 may be stored indifferent communication channels or other storage types. In this aspect,the general computing device 804 is executing an email application 660that utilizes the improved touchable user interface for a softwareapplication. Further, in this aspect, the tablet 806 is executing a wordprocessing application 662 utilizing the improved touchable userinterface for a software application. Additionally, in this aspect, themobile computing device 808 is executing a spreadsheet applicationutilizing the improved touchable user interface for a softwareapplication. The improved touchable user interface for a softwareapplication and a method for generating the improved touchable userinterface are described in detail above and illustrated in FIGS. 1-3.For example, various documents may be stored using a directory service822, a web portal 824, a mailbox service 826, an instant messaging store828, or a social networking site 830.

FIG. 9 illustrates an exemplary tablet computing device 900 that mayexecute one or more aspects disclosed herein. In addition, the aspectsand functionalities described herein may operate over distributedsystems (e.g., cloud-based computing systems), where applicationfunctionality, memory, data storage and retrieval and various processingfunctions may be operated remotely from each other over a distributedcomputing network, such as the Internet or an intranet. User interfacesand information of various types may be displayed via on-board computingdevice displays or via remote display units associated with one or morecomputing devices. For example user interfaces and information ofvarious types may be displayed and interacted with on a wall surfaceonto which user interfaces and information of various types areprojected. Interaction with the multitude of computing systems withwhich aspects of the invention may be practiced include, keystrokeentry, touch screen entry, voice or other audio entry, gesture entrywhere an associated computing device is equipped with detection (e.g.,camera) functionality for capturing and interpreting user gestures forcontrolling the functionality of the computing device, and the like.

Among other examples, the present disclosure presents systems fordisplaying a touchable user interface at a display device, comprising:identifying available application space on the display device; comparingan amount of available application space with an amount of spacerequired for displaying one or more user interface elements; determiningwhether sufficient space is available for the amount of space requiredfor displaying the one or more user interface elements; and when it isdetermined that sufficient space is not available, adjusting visibledisplay of the one or more user interface elements such that at leastone of the one or more user interface elements is scaled, re-positionedor removed. In further examples, the visible display of the one or moreuser interface elements is displayed as a grid layout with one or morerows and one or more columns. In further examples, the one or more rowsand the one or more columns are scaled based on at least a screen sizeof the display device. In further examples, the one or more rows and theone or more columns are scaled based on at least how many of the one ormore user interface elements can be displayed on the display device. Infurther examples, a display size of the one or more user interfaceelements does not change when a screen size of the display devicechanges such that a number of the one or more user interface elementsdisplayed changes (e.g., a number of the one or more user interfaceelements is/are re-positioned). In further examples, a display size ofthe one or more user interface elements changes when a screen size ofthe display device changes such that a number of the one or more userinterface elements displayed does not change (e.g., a number of the oneor more user interface elements is/are scaled). In further examples, ascreen size of the display device changes based on at least one of auser selection of a desired screen size, a change in a display screen ofthe display device, and a change in the display device orientation. Infurther examples, identifying available application space on the displaydevice comprises identifying a change in an amount of availableapplication space. In further examples, comparing an amount of availableapplication space with an amount of space required for one or more userinterface elements comprises calculating a layout for the touchable userinterface. In further examples, calculating a layout for the touchableuser interface comprises determining a size of the one or more userinterface elements. In further examples, the adjusted visible displayincludes at least the one or more user interface elements and acontextual panel having selectable controls.

Further aspects disclosed herein provides exemplary systems and methodsfor displaying a user interface progress experience on a touchable userinterface of a display device, comprising: displaying, on a canvas ofthe display device, one or more user interface elements; displaying, ona contextual panel of the display device, a plurality of selectablecontrols; receiving, at the touchable user interface, a selection of atleast one action command, wherein the at least one action command isassociated with the one or more user interface elements; performing theselected at least one action command; determining whether the selectedat least one action command has been completed while performing theselected at least one action command; when it is determined that theselected at least one action command has not been completed, determiningwhether a threshold value has been met; and when it is determined thatthe threshold value has been met, displaying the user interface progressexperience on the touchable user interface of the display device. Infurther examples, receiving the selection of at least one action commandcomprises detecting at least one of a single touch and hand gesture ofthe one or more user interface elements or one of the plurality ofselectable controls on the touchable user interface. In furtherexamples, the selectable controls include functionality for executingthe at least one action command. In further examples, the at least oneaction command includes at least one of opening, saving, creating,printing, closing, and sharing. In further examples, the threshold valueis based on avoiding flickering of the user interface progressexperience when the at least one action command is performed andcompleted in less than two seconds. In further examples, the userinterface progress experience indicates a status of the selected atleast one action command as the at least one action command isperformed. In further examples, the status of the selected at least oneaction command includes text displayed on the touchable user interfaceof the display device. In further examples, when it is determined thatthe selected at least one action command has been completed, hiding theuser interface progress experience from the touchable user interface ofthe display device.

Additional aspects disclosed herein provide exemplary methods fordisplaying a touchable user interface at a display device, comprising:identifying available application space on the display device; comparingan amount of available application space with an amount of spacerequired for displaying one or more user interface elements; determiningwhether sufficient space is available for the amount of space requiredfor displaying the one or more user interface elements; and when it isdetermined that sufficient space is not available, adjusting visibledisplay of the one or more user interface elements such that at leastone of the one or more user interface elements is scaled, re-positioned,or removed, and wherein the visible display of the one or more userinterface elements is displayed as a grid layout with one or more rowsand one or more columns.

Aspects of the present disclosure, for example, are described above withreference to block diagrams and/or operational illustrations of methods,systems, and computer program products according to aspects of thedisclosure. The functions/acts noted in the blocks may occur out of theorder as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

The description and illustration of one or more aspects provided in thisapplication are not intended to limit or restrict the scope of thedisclosure as claimed in any way. The aspects, examples, and detailsprovided in this application are considered sufficient to conveypossession and enable others to make and use the best mode of claimeddisclosure. The claimed disclosure should not be construed as beinglimited to any aspect, example, or detail provided in this application.Regardless of whether shown and described in combination or separately,the various features (both structural and methodological) are intendedto be selectively included or omitted to produce an aspect with aparticular set of features. Having been provided with the descriptionand illustration of the present application, one skilled in the art mayenvision variations, modifications, and alternate aspects falling withinthe spirit of the broader aspects of the general inventive conceptembodied in this application that do not depart from the broader scopeof the claimed disclosure.

Additionally, while the aspects may be described in the general contextof improved touchable user interfaces that execute in conjunction withan application program that runs on an operating system on a computingdevice, those skilled in the art will recognize that aspects may also beimplemented in combination with other program modules. In furtheraspects, the aspects disclosed herein may be implemented in hardware.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Moreover, those skilled inthe art will appreciate that aspects may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and comparablecomputing devices. Aspects may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inboth local and remote memory storage devices.

Aspects may be implemented as a computer-implemented process (method), acomputing system, or as an article of manufacture, such as a computerprogram product or computer readable media. The computer program productmay be a computer storage medium readable by a computer system andencoding a computer program that comprises instructions for causing acomputer or computing system to perform example process(es). Thecomputer-readable storage medium can for example be implemented via oneor more of a volatile computer memory, a non-volatile memory, a harddrive, a flash drive, a floppy disk, or compact servers, an applicationexecuted on a single computing device, and comparable systems.

What is claimed is:
 1. A system comprising: at least one processor; andmemory encoding computer executable instructions that, when executed bythe at least one processor, perform a method for displaying a touchableuser interface at a display device, the method comprising: identifying,on the display device, available application space for an application,wherein the available application space corresponds to a first windowsize for the application, and the available application spacecorresponds to a first arrangement of one or more rows and columns;using a priority list to determine one or more document thumbnails andone or more selectable controls to be displayed in the firstarrangement, wherein the priority list automatically identifies a firstset of document thumbnails and selectable controls based on the firstwindow size, the priority list automatically identifies a second set ofdocument thumbnails and selectable controls to be displayed based on asecond window size, and the priority list calculates scaling up to apredetermined maximum window size and/or down to a predetermined minimumwindow size; determining whether an amount of the available applicationspace is sufficient for displaying the one or more document thumbnailsby comparing the amount of the available application space with anamount of space required for displaying the one or more documentthumbnails; and when it is determined that sufficient space is notavailable, adjusting the first arrangement into a different secondarrangement of the one or more rows and columns based on the firstwindow size, wherein at least one of the one or more document thumbnailsis re-positioned or removed.
 2. The system of claim 1, wherein thevisible display of the one or more thumbnails is displayed as a gridlayout with one or more rows and one or more columns.
 3. The system ofclaim 2, wherein the one or more rows and the one or more columns arescaled based on at least a screen size of the display device.
 4. Thesystem of claim 2, wherein the one or more rows and the one or morecolumns are scaled based on at least how many of the one or morethumbnails can be displayed on the display device.
 5. The system ofclaim 1, wherein a display size of the one or more thumbnails does notchange when a screen size of the display device changes such that anumber of the one or more thumbnails displayed changes.
 6. The system ofclaim 1, wherein a display size of the one or more thumbnails changeswhen a screen size of the display device changes such that a number ofthe one or more thumbnails displayed does not change.
 7. The system ofclaim 1, wherein a screen size of the display device changes based on atleast one of a user selection of a desired screen size, a change in adisplay screen of the display device, and a change in the display deviceorientation.
 8. The system of claim 1, wherein identifying availableapplication space on the display device comprises identifying a changein an amount of available application space.
 9. The system of claim 1,wherein comparing an amount of available application space with anamount of space required for one or more thumbnails comprisescalculating a layout for the touchable user interface.
 10. The system ofclaim 9, wherein calculating a layout for the touchable user interfacecomprises determining a size of the one or more thumbnails.
 11. Thesystem of claim 1, wherein the adjusted visible display includes atleast the one or more thumbnails and a contextual panel havingselectable controls.
 12. A computer storage device havingcomputer-executable instructions that, when executed by a processor,perform a method for displaying a user interface progress experience ona touchable user interface of a display device, the method comprising:displaying, on a canvas of the display device, one or more documentthumbnails, wherein the one or more document thumbnails correspond toone or more applications provided by the display device, and wherein anarrangement of the one or more document thumbnails is based on apriority list that calculates scaling up to a predetermined maximumwindow size and/or down to a predetermined minimum window size;displaying, on a contextual panel of the display device, a plurality ofselectable controls; receiving, at the touchable user interface, aselection of at least one action command associated with the one or moredocument thumbnails; initiating the selected at least one actioncommand; determining whether the selected at least one action commandhas been completed; when it is determined that the selected at least oneaction command has not been completed, determining a current amount ofexecution time for the at least one action and comparing the currentamount of execution time to a threshold value to determine whether thethreshold value has been met; and in response to determining that thethreshold value has been met, automatically displaying a user interfaceprogress experience on the touchable user interface of the displaydevice, wherein the user interface progress experience indicates astatus of the selected at least one action as the selected at least oneaction is performed.
 13. The computer storage device of claim 12,wherein receiving the selection of at least one action command comprisesdetecting at least one of a single touch and hand gesture of the one ormore thumbnails or one of the plurality of selectable controls on thetouchable user interface.
 14. The computer storage device of claim 12,wherein the selectable controls include functionality for executing theat least one action command.
 15. The computer storage device of claim12, wherein the at least one action command includes at least one ofopening, saving, creating, printing, closing, and sharing.
 16. Thecomputer storage device of claim 12, wherein the threshold value isbased on avoiding flickering of the user interface progress experiencewhen the at least one action command is performed and completed in lessthan two seconds.
 17. The computer storage device of claim 12, whereinthe user interface progress experience indicates a status of theselected at least one action command as the at least one action commandis performed.
 18. The computer storage device of claim 17, wherein thestatus of the selected at least one action command includes textdisplayed on the touchable user interface of the display device.
 19. Thecomputer storage device of claim 12, further comprising, when it isdetermined that the selected at least one action command has beencompleted, hiding the user interface progress experience from thetouchable user interface of the display device.
 20. A method fordisplaying a touchable user interface at a display device, the methodcomprising: identifying available application space on the displaydevice, wherein the available application space corresponds to a firstwindow size for an application wherein the identification includes usinga priority list to determine one or more document thumbnails and one ormore selectable controls to be displayed by the display device, whereinthe priority list identifies a first set of document thumbnails andselectable controls based on the first window size, the priority listidentifies a second set of document thumbnails and selectable controlsto be displayed based on a second window size, and the priority listcalculates scaling up to a predetermined maximum window size and/or downto a predetermined minimum window size; comparing an amount of availableapplication space with an amount of space required for displaying one ormore document thumbnails; based on the comparison, determining whetherthe amount of the available application space is sufficient fordisplaying the one or more document thumbnails; and when it isdetermined that sufficient space is not available, adjusting the firstarrangement into a different second arrangement of the one or more rowsand columns based on the first window size, wherein at least one of theone or more document thumbnails is re-positioned or removed.